home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950726-19950929
/
000398_news@columbia.edu_Tue Sep 19 03:29:01 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA25858
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Wed, 20 Sep 1995 05:29:08 -0400
Received: by apakabar.cc.columbia.edu id AA12007
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Wed, 20 Sep 1995 05:29:07 -0400
Path: news.columbia.edu!news.cs.columbia.edu!pipeline!uunet!in1.uu.net!usc!usc!howland.reston.ans.net!swrinde!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Progress on MSK 3.14 and Linux 1.2.8 problem
Message-Id: <1995Sep19.092901.61603@cc.usu.edu>
Date: 19 Sep 95 09:29:01 MDT
References: <43c0ds$hvk@apakabar.cc.columbia.edu> <43idul$j5@apakabar.cc.columbia.edu>
Organization: Utah State University
Lines: 27
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <43idul$j5@apakabar.cc.columbia.edu>, chaiklin@merhaba.cc.columbia.edu (Seth Chaiklin) writes:
> In article <1995Sep15.113320.61386@cc.usu.edu>,
> Joe Doupnik <jrd@cc.usu.edu> wrote:
>>In article <43c0ds$hvk@apakabar.cc.columbia.edu>, chaiklin@merhaba.cc.columbia.edu (Seth Chaiklin) writes:
>>> This message is a continuation of my inquest into why I have
>>> had problems with MSK 3.14 and Linux connections.
>>>
>>> I have made some progress, I believe in delimiting the problem,
>>> so I will start a fresh thread.
>> <snipping off the details>
>
>> I think the logic is still muddled here. A simple suggestion is
>>try a connection between MSK and a non-Linux machine, and observe the
>>behavior. It's a substitution test.
>
> If I understood correctly, I attempted this test. I connected
> between MSK and a SunOS 4.1.3 machine, let it sit for two hours and
> there were no problems.
>
> So what do you conclude?
------------
So far I would conclude that your version of Linux has problems
in its TCP/IP stack. And that the problems are sensitive to whether or
not an ARP reply has the IP address of the requestor or 0.0.0.0 there
(current MSK has the IP address, previous v3.14 did not by mistake).
Anyone else have some ideas? Dan?
Joe D.